TRAVERSE Global v11.1

TRAVERSE Payment System (TPS) Overview

Payment Service Integration for TRAVERSE® (TPS) manages the interaction with external payment providers, including the encryption/decryption of any values shared between them and TRAVERSE. The payment service supports both card present and hosted payment forms.

Regular back office workflow is not dependent upon provider-based processing or validation. Additional workflow management utilizes an AR Payment Method type to identify external payments. Most processing, reporting, and inquiry systems within TRAVERSE are unaffected.

The TRAVERSE Payment System does not store any sensitive account information for external payments for PCI DSS compliance. All information is retained by the payment provider. Data for payment methods and transactions are stored in dedicated tables to isolate the service data from base processing.

Setup

The setup process for TPS follows the typical setup process for other functions in TRAVERSE, beginning with installing Build 18296 or higher that includes credit card integration.

  • You must have an account with the payment service to obtain the credentials required for TRAVERSE. Contact your software solution provider for more information.
  • If you need assistance with TPS setup, contact your software solution provider or TRAVERSE support.
  • If you use EMV card readers, work with your payment service provider to install the required software to connect and run the card reader.

Workflow

When consumers make an electronic purchase using a credit or debit card (or a digital or mobile wallet backed by stored credentials), a variety of players from banks to credit card companies to payment processors cooperate to facilitate the transaction. The process can vary depending on the nature of the gateway and payment.

Examples